Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 592cc166f099b647b4d5af50de89eff0e0c37ed624a916578e221f2774f5bcfe

Tx prefix hash: 57fe684d9a411d61bdc8f03581a2278ef9503945e6441e9e661c682425f6f5bf
Tx public key: b21065ba71fd3e384892b2a7c7ba36d220dc62c09b328cd9297c2533874382fc
Timestamp: 1731584947 Timestamp [UCT]: 2024-11-14 11:49:07 Age [y:d:h:m:s]: 00:220:09:58:22
Block: 1153511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157196 RingCT/type: yes/0
Extra: 01b21065ba71fd3e384892b2a7c7ba36d220dc62c09b328cd9297c2533874382fc021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7189e5b35e4bd5286d2de9088af3d6b33febb64ec7208796fd0a098aa521f923 0.600000000000 1639120 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": 1153521, "vin": [ { "gen": { "height": 1153511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7189e5b35e4bd5286d2de9088af3d6b33febb64ec7208796fd0a098aa521f923" } } ], "extra": [ 1, 178, 16, 101, 186, 113, 253, 62, 56, 72, 146, 178, 167, 199, 186, 54, 210, 32, 220, 98, 192, 155, 50, 140, 217, 41, 124, 37, 51, 135, 67, 130, 252, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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