Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 721148dd24fc10b30a14a4268e48b4bbe34c4711a9d186e5d05a2465035321f7

Tx prefix hash: ac91d51435badd80a81452711c59f96596f2c163cb8aa066c26843e54590f674
Tx public key: f20152c07890f7236bd3461045716d83d02061e7f5c6648de2cd0a5b08e7d2f4
Timestamp: 1743436471 Timestamp [UCT]: 2025-03-31 15:54:31 Age [y:d:h:m:s]: 00:234:20:07:24
Block: 1251364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165570 RingCT/type: yes/0
Extra: 01f20152c07890f7236bd3461045716d83d02061e7f5c6648de2cd0a5b08e7d2f4021100000005def6842b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f7f72c4904a9adf818f2e7466cc55971b7518b545789f4d97a4f48f4cf4d9a5 0.600000000000 1738427 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": 1251374, "vin": [ { "gen": { "height": 1251364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f7f72c4904a9adf818f2e7466cc55971b7518b545789f4d97a4f48f4cf4d9a5" } } ], "extra": [ 1, 242, 1, 82, 192, 120, 144, 247, 35, 107, 211, 70, 16, 69, 113, 109, 131, 208, 32, 97, 231, 245, 198, 100, 141, 226, 205, 10, 91, 8, 231, 210, 244, 2, 17, 0, 0, 0, 5, 222, 246, 132, 43, 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