Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32253e924526fa6e4ae72fa86a1d5fb66c930fb868b67d7681d8f1fb2cae9002

Tx prefix hash: 46fa8eca131b82e59d75369a692b35c60869cb412615c411ed46e94490e66a7b
Tx public key: 626d81b9b92fbb98724fe8b1fdc5368422cb04765ad577dc8ee4cf5b955a06fc
Timestamp: 1747805411 Timestamp [UCT]: 2025-05-21 05:30:11 Age [y:d:h:m:s]: 00:184:06:32:01
Block: 1287548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129386 RingCT/type: yes/0
Extra: 01626d81b9b92fbb98724fe8b1fdc5368422cb04765ad577dc8ee4cf5b955a06fc0211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b43caf45f70369cdf21570e2a0bd85c1da3d01447e9f41eba6a082252d94460 0.600000000000 1775015 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": 1287558, "vin": [ { "gen": { "height": 1287548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b43caf45f70369cdf21570e2a0bd85c1da3d01447e9f41eba6a082252d94460" } } ], "extra": [ 1, 98, 109, 129, 185, 185, 47, 187, 152, 114, 79, 232, 177, 253, 197, 54, 132, 34, 203, 4, 118, 90, 213, 119, 220, 142, 228, 207, 91, 149, 90, 6, 252, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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