Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fc2f32a5b048e6450b65bafa4906e88f8a97b9314cb7ff81ce1443e9ba4d66d

Tx prefix hash: 03a3e892f09ee1b5f2bd47c93ada41fa9a047032c2d8fe0376d780516a30fa7a
Tx public key: d15694ae720f2b395c9d5cc51d3ac74ae543c0eba76b74c5b14793ee83353996
Timestamp: 1736478830 Timestamp [UCT]: 2025-01-10 03:13:50 Age [y:d:h:m:s]: 00:068:07:37:00
Block: 1194032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48623 RingCT/type: yes/0
Extra: 01d15694ae720f2b395c9d5cc51d3ac74ae543c0eba76b74c5b14793ee8335399602110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff482c3b424fa6bae1821261714747a2f086c9d8fa43dcebed76407534c4d94c 0.600000000000 1680599 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": 1194042, "vin": [ { "gen": { "height": 1194032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff482c3b424fa6bae1821261714747a2f086c9d8fa43dcebed76407534c4d94c" } } ], "extra": [ 1, 209, 86, 148, 174, 114, 15, 43, 57, 92, 157, 92, 197, 29, 58, 199, 74, 229, 67, 192, 235, 167, 107, 116, 197, 177, 71, 147, 238, 131, 53, 57, 150, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 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