Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 247bcae775305d453ad8b2f6afd19621026f991201018e24ac7f4b7043cde1f8

Tx prefix hash: 58864baf31630b9cbbb24a8231e5cc0c22a454e69dce308e37a91191d1f7f0c8
Tx public key: 0e6d6b6d56dcc02aeb118dfdb8075b94898b7b199325654738c6123ee5ecd9ed
Timestamp: 1751147524 Timestamp [UCT]: 2025-06-28 21:52:04 Age [y:d:h:m:s]: 00:144:10:09:25
Block: 1314783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101324 RingCT/type: yes/0
Extra: 010e6d6b6d56dcc02aeb118dfdb8075b94898b7b199325654738c6123ee5ecd9ed021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be284dd8db45fd00cdd4251f4d0f79758f0eddd58b92b0c4d64a25dff907fe41 0.600000000000 1802434 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": 1314793, "vin": [ { "gen": { "height": 1314783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be284dd8db45fd00cdd4251f4d0f79758f0eddd58b92b0c4d64a25dff907fe41" } } ], "extra": [ 1, 14, 109, 107, 109, 86, 220, 192, 42, 235, 17, 141, 253, 184, 7, 91, 148, 137, 139, 123, 25, 147, 37, 101, 71, 56, 198, 18, 62, 229, 236, 217, 237, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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