Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: fb12ab71ddafc9d021f2712fc0320b0e52bff12371ac2f3652415134ecae628e

Tx prefix hash: 9d203a87810901207e2d8dfc8e75526f062381c7ebb5a9fd39985861738af83e
Tx public key: 2dbac5f495ec368a8484a0e1adb79b5ae59e73a7da7998d17b931fd4e14b13cf
Timestamp: 1723084697 Timestamp [UCT]: 2024-08-08 02:38:17 Age [y:d:h:m:s]: 00:143:14:02:17
Block: 1083131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102713 RingCT/type: yes/0
Extra: 012dbac5f495ec368a8484a0e1adb79b5ae59e73a7da7998d17b931fd4e14b13cf021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e4d3dd4a0b8ebaaa2d686508e370a812322b9d452d089748ff29d0d4bab1a72 0.600000000000 1556966 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1083141, "vin": [ { "gen": { "height": 1083131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e4d3dd4a0b8ebaaa2d686508e370a812322b9d452d089748ff29d0d4bab1a72" } } ], "extra": [ 1, 45, 186, 197, 244, 149, 236, 54, 138, 132, 132, 160, 225, 173, 183, 155, 90, 229, 158, 115, 167, 218, 121, 152, 209, 123, 147, 31, 212, 225, 75, 19, 207, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8