Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 738f7a6dabd5f3ea2f49bd86def26314b0e09127d7f054b2ec79dd412b6d9dc1

Tx prefix hash: 988706cb9173c3e1af1ad726e0cc652317866f315d93ddc81d32c77b256a0d72
Tx public key: 2be289519e95f1136a3bd595337c1a9bbcf346045bfb9c569bbf57d2a5e4b626
Timestamp: 1677678973 Timestamp [UCT]: 2023-03-01 13:56:13 Age [y:d:h:m:s]: 01:317:21:00:18
Block: 707574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488122 RingCT/type: yes/0
Extra: 012be289519e95f1136a3bd595337c1a9bbcf346045bfb9c569bbf57d2a5e4b6260211000000065029cbac000000000000000000

1 output(s) for total of 2.776601233000 dcy

stealth address amount amount idx
00: 9a014cc9a977af570893a2fe0828317e7b4d3b6e754f6e60a9dc81a6906a6d81 2.776601233000 1151389 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": 707584, "vin": [ { "gen": { "height": 707574 } } ], "vout": [ { "amount": 2776601233, "target": { "key": "9a014cc9a977af570893a2fe0828317e7b4d3b6e754f6e60a9dc81a6906a6d81" } } ], "extra": [ 1, 43, 226, 137, 81, 158, 149, 241, 19, 106, 59, 213, 149, 51, 124, 26, 155, 188, 243, 70, 4, 91, 251, 156, 86, 155, 191, 87, 210, 165, 228, 182, 38, 2, 17, 0, 0, 0, 6, 80, 41, 203, 172, 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