Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00c9d3bad85d63d1188c37d985630d0c3e93290ad12f962b81227aafde632071

Tx prefix hash: 3e68a45845dd496b02f8a8427124c0857aeeea68f285f6cc592711d3d2e7410d
Tx public key: 76bdf637a9227d1f1fc66e6dec71e44f35aa80b2e6fb0508965436ab1cfc416d
Timestamp: 1710446825 Timestamp [UCT]: 2024-03-14 20:07:05 Age [y:d:h:m:s]: 01:093:01:21:49
Block: 978375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327426 RingCT/type: yes/0
Extra: 0176bdf637a9227d1f1fc66e6dec71e44f35aa80b2e6fb0508965436ab1cfc416d02110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 332985dcf7957a4536d8db8b875929668a00d8459be4ecc95ea4493f03231c1d 0.600000000000 1438400 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": 978385, "vin": [ { "gen": { "height": 978375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "332985dcf7957a4536d8db8b875929668a00d8459be4ecc95ea4493f03231c1d" } } ], "extra": [ 1, 118, 189, 246, 55, 169, 34, 125, 31, 31, 198, 110, 109, 236, 113, 228, 79, 53, 170, 128, 178, 230, 251, 5, 8, 150, 84, 54, 171, 28, 252, 65, 109, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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