Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3460f8cc6ffaae20e20688da488ce33337eb9cb7044ab7e613d81ff2d0bbc44

Tx prefix hash: 8fae90b8ddf7ccc0bc4b0f3d925aec916665c8dfb0a78728bef8449e0b2c0504
Tx public key: d0bff8a12a934892f245849da88c9a73b55b060413c636a4a6d30da2f31b2121
Timestamp: 1707957991 Timestamp [UCT]: 2024-02-15 00:46:31 Age [y:d:h:m:s]: 00:333:01:47:36
Block: 957715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238443 RingCT/type: yes/0
Extra: 01d0bff8a12a934892f245849da88c9a73b55b060413c636a4a6d30da2f31b21210211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bafcecf44ec131f7de5f9688b26234c48cd3ad845669a081264692cfa833ca9 0.600000000000 1417064 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": 957725, "vin": [ { "gen": { "height": 957715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bafcecf44ec131f7de5f9688b26234c48cd3ad845669a081264692cfa833ca9" } } ], "extra": [ 1, 208, 191, 248, 161, 42, 147, 72, 146, 242, 69, 132, 157, 168, 140, 154, 115, 181, 91, 6, 4, 19, 198, 54, 164, 166, 211, 13, 162, 243, 27, 33, 33, 2, 17, 0, 0, 0, 1, 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