Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2822a2502153052579ab1dbf193272beba066fc229f6cb272b6d8281e767d54e

Tx prefix hash: 1b1e96acb5d66e5f45988e5ca6b93f23be07d83640cdd8986f29302e6d0b556b
Tx public key: 7434b588c0bcc62f741ee886a191c83ca216f3f9ba0be8d9e9e3a3bdc23c925e
Timestamp: 1697019315 Timestamp [UCT]: 2023-10-11 10:15:15 Age [y:d:h:m:s]: 00:235:02:47:49
Block: 867240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168222 RingCT/type: yes/0
Extra: 017434b588c0bcc62f741ee886a191c83ca216f3f9ba0be8d9e9e3a3bdc23c925e02110000000e4b8f5122000000000000000000

1 output(s) for total of 0.821247202000 dcy

stealth address amount amount idx
00: 5e59fd034fbeb10a9d135abea0209b7e3478976eabe64e1c8eee21b1c64ab00e 0.821247202000 1321906 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": 867250, "vin": [ { "gen": { "height": 867240 } } ], "vout": [ { "amount": 821247202, "target": { "key": "5e59fd034fbeb10a9d135abea0209b7e3478976eabe64e1c8eee21b1c64ab00e" } } ], "extra": [ 1, 116, 52, 181, 136, 192, 188, 198, 47, 116, 30, 232, 134, 161, 145, 200, 60, 162, 22, 243, 249, 186, 11, 232, 217, 233, 227, 163, 189, 194, 60, 146, 94, 2, 17, 0, 0, 0, 14, 75, 143, 81, 34, 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