Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc7464b7a47735ddf682ebf8493eb0df61e833f64b44bef709f5cbb3b49bbf86

Tx prefix hash: 3617112d23893d6175f247c13ac8f0022c3f1b0f0606c5e28964e841bf362281
Tx public key: e31abd6e24dfa14b4558e132e33b6722d2939cfd9f3a6d6302af1e82e80caf68
Timestamp: 1721810963 Timestamp [UCT]: 2024-07-24 08:49:23 Age [y:d:h:m:s]: 00:329:23:48:45
Block: 1072564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235672 RingCT/type: yes/0
Extra: 01e31abd6e24dfa14b4558e132e33b6722d2939cfd9f3a6d6302af1e82e80caf6802110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d56697473b8b39a22c1ad7b5f5d8b4fe56e59fa8034cb9192291da468078fe5 0.600000000000 1545039 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": 1072574, "vin": [ { "gen": { "height": 1072564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d56697473b8b39a22c1ad7b5f5d8b4fe56e59fa8034cb9192291da468078fe5" } } ], "extra": [ 1, 227, 26, 189, 110, 36, 223, 161, 75, 69, 88, 225, 50, 227, 59, 103, 34, 210, 147, 156, 253, 159, 58, 109, 99, 2, 175, 30, 130, 232, 12, 175, 104, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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