Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 968fc1fb1c366f315ae023c5f55d015256938bdd9c33f9db900ce1f3c2937664

Tx prefix hash: e014ef9aacf6cd5347d86192deafa8c6a94993411c8ef579ffc0d09aa0f18830
Tx public key: a8576bbdc99b443c9b2db5a01712a3620a95303f86d37f2002d10dcbfcc0e503
Timestamp: 1714218785 Timestamp [UCT]: 2024-04-27 11:53:05 Age [y:d:h:m:s]: 00:324:22:15:15
Block: 1009622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232288 RingCT/type: yes/0
Extra: 01a8576bbdc99b443c9b2db5a01712a3620a95303f86d37f2002d10dcbfcc0e5030211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 047e2653ef4ffed6d49e080eecd0e77940f81c39efe28f23e01da33a66ca7e21 0.600000000000 1471350 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": 1009632, "vin": [ { "gen": { "height": 1009622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "047e2653ef4ffed6d49e080eecd0e77940f81c39efe28f23e01da33a66ca7e21" } } ], "extra": [ 1, 168, 87, 107, 189, 201, 155, 68, 60, 155, 45, 181, 160, 23, 18, 163, 98, 10, 149, 48, 63, 134, 211, 127, 32, 2, 209, 13, 203, 252, 192, 229, 3, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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