Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb2a22830a43d6685bf01611bfb84019927866eaed4d0e6b0fe5bf45be5d945b

Tx prefix hash: af68662dca5a9c675ee664a55aefebd008903fd8dc49ce6c842f2cb6150ef7a7
Tx public key: a18a412ffb7733b9b714f5356df28fe8eb852960c742121bf7a089954cdeba06
Timestamp: 1736016466 Timestamp [UCT]: 2025-01-04 18:47:46 Age [y:d:h:m:s]: 00:300:00:31:42
Block: 1190209 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211924 RingCT/type: yes/0
Extra: 01a18a412ffb7733b9b714f5356df28fe8eb852960c742121bf7a089954cdeba060211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71b2e3adc6036658d9e58207e5aa252311e8b475f34e53707763c85f4f2b0a93 0.600000000000 1676724 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": 1190219, "vin": [ { "gen": { "height": 1190209 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71b2e3adc6036658d9e58207e5aa252311e8b475f34e53707763c85f4f2b0a93" } } ], "extra": [ 1, 161, 138, 65, 47, 251, 119, 51, 185, 183, 20, 245, 53, 109, 242, 143, 232, 235, 133, 41, 96, 199, 66, 18, 27, 247, 160, 137, 149, 76, 222, 186, 6, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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