Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da47a73270aa5a75b8990a88797b94ec48414c009df03e61b4cc01113a24208b

Tx prefix hash: 1b4c89dcd7176f0c34a0c2914d0d0900cbf9989e6bfc922c9a1b5a95621b34b0
Tx public key: e6ffee0a2123a2da289e680fe22d4bbca3f7a535fea74ca8654cccc415e7245e
Timestamp: 1747262106 Timestamp [UCT]: 2025-05-14 22:35:06 Age [y:d:h:m:s]: 00:146:04:13:38
Block: 1283046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102104 RingCT/type: yes/0
Extra: 01e6ffee0a2123a2da289e680fe22d4bbca3f7a535fea74ca8654cccc415e7245e02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f80bad18a429b05fcaf75d909b1a515cd9004362f9c8ce83c8f034176e21d563 0.600000000000 1770463 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": 1283056, "vin": [ { "gen": { "height": 1283046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f80bad18a429b05fcaf75d909b1a515cd9004362f9c8ce83c8f034176e21d563" } } ], "extra": [ 1, 230, 255, 238, 10, 33, 35, 162, 218, 40, 158, 104, 15, 226, 45, 75, 188, 163, 247, 165, 53, 254, 167, 76, 168, 101, 76, 204, 196, 21, 231, 36, 94, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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