Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9c7ac92f4daf2b603907699c12cc957d3b47362b67593c76566373dfc11722e

Tx prefix hash: 9b5684070c3a7138e0ae63f521c203dab782878e5b1c675fc3596e40832383b5
Tx public key: cf0f0184c1ae3f2a5ccd1e8791b30b2868bf3ac35886f843e353ece280601c78
Timestamp: 1709204856 Timestamp [UCT]: 2024-02-29 11:07:36 Age [y:d:h:m:s]: 00:331:22:44:44
Block: 968064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237569 RingCT/type: yes/0
Extra: 01cf0f0184c1ae3f2a5ccd1e8791b30b2868bf3ac35886f843e353ece280601c780211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f97f56d7491bb5c7be7479f04c4382d6381c57fd15b7f045dcc26c5af9d723eb 0.600000000000 1427861 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": 968074, "vin": [ { "gen": { "height": 968064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f97f56d7491bb5c7be7479f04c4382d6381c57fd15b7f045dcc26c5af9d723eb" } } ], "extra": [ 1, 207, 15, 1, 132, 193, 174, 63, 42, 92, 205, 30, 135, 145, 179, 11, 40, 104, 191, 58, 195, 88, 134, 248, 67, 227, 83, 236, 226, 128, 96, 28, 120, 2, 17, 0, 0, 0, 3, 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