Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd19977582019aaebf09760ba2a32817fa9c11da7d2284f53ad8311c1c6c1107

Tx prefix hash: a02bc256640eda282c4f73d634be20b3fd96883d5ce4efab9623e666335faf6e
Tx public key: 0eb75919fdc97730cc37a8c60095412f02e5bf565a60826713d8ccf522d38cbb
Timestamp: 1729135555 Timestamp [UCT]: 2024-10-17 03:25:55 Age [y:d:h:m:s]: 01:021:17:30:04
Block: 1133298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273888 RingCT/type: yes/0
Extra: 010eb75919fdc97730cc37a8c60095412f02e5bf565a60826713d8ccf522d38cbb02110000000b3cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 455fef01bb58210d8e21a6e6c75ba89f498b7c02a017103194b9dc2c7a7b7fe0 0.600000000000 1616393 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": 1133308, "vin": [ { "gen": { "height": 1133298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "455fef01bb58210d8e21a6e6c75ba89f498b7c02a017103194b9dc2c7a7b7fe0" } } ], "extra": [ 1, 14, 183, 89, 25, 253, 201, 119, 48, 204, 55, 168, 198, 0, 149, 65, 47, 2, 229, 191, 86, 90, 96, 130, 103, 19, 216, 204, 245, 34, 211, 140, 187, 2, 17, 0, 0, 0, 11, 60, 208, 252, 6, 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