Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 077c1a7d7613b3eb502a14a43a6e2c636ac61bddecea7c18ec57225757ec7923

Tx prefix hash: 32599edb58b7f5e3d30e775a155b9aba56b6bb355fedca6408b89944ab3e32d0
Tx public key: a1e8f451ffb0e95bda25606ba027a59bc07adbe2b59c8ce624097ff622fc2e8e
Timestamp: 1639197396 Timestamp [UCT]: 2021-12-11 04:36:36 Age [y:d:h:m:s]: 03:324:20:52:32
Block: 392964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1008643 RingCT/type: yes/0
Extra: 01a1e8f451ffb0e95bda25606ba027a59bc07adbe2b59c8ce624097ff622fc2e8e021100000001e9564d6f000000000000000000

1 output(s) for total of 30.615933269000 dcy

stealth address amount amount idx
00: f901e3d6f703aec0db71eda8f7bb81cca5caef70c4c64108b39b1be5d38324e6 30.615933269000 790007 of 0

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": 392974, "vin": [ { "gen": { "height": 392964 } } ], "vout": [ { "amount": 30615933269, "target": { "key": "f901e3d6f703aec0db71eda8f7bb81cca5caef70c4c64108b39b1be5d38324e6" } } ], "extra": [ 1, 161, 232, 244, 81, 255, 176, 233, 91, 218, 37, 96, 107, 160, 39, 165, 155, 192, 122, 219, 226, 181, 156, 140, 230, 36, 9, 127, 246, 34, 252, 46, 142, 2, 17, 0, 0, 0, 1, 233, 86, 77, 111, 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