Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 598a27047184fe71061b15f734bb2c66f7d2154b42a02d57d879cbe2feb0fdc2

Tx prefix hash: e350cbcc9d6455e15e9b4c3dea1fac5523217a1e452f85033bb12420a289e5aa
Tx public key: 7c9808f3887e739d0c19cb99e63c46ee37811d26d67d9fb59057726b57037430
Timestamp: 1707262817 Timestamp [UCT]: 2024-02-06 23:40:17 Age [y:d:h:m:s]: 01:087:02:42:45
Block: 951944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323337 RingCT/type: yes/0
Extra: 017c9808f3887e739d0c19cb99e63c46ee37811d26d67d9fb59057726b5703743002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14c99f127c5b09a758035d9455bcd68189bc64ad9f6b0f4e8eb8e1d4199ca9b5 0.600000000000 1410794 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": 951954, "vin": [ { "gen": { "height": 951944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14c99f127c5b09a758035d9455bcd68189bc64ad9f6b0f4e8eb8e1d4199ca9b5" } } ], "extra": [ 1, 124, 152, 8, 243, 136, 126, 115, 157, 12, 25, 203, 153, 230, 60, 70, 238, 55, 129, 29, 38, 214, 125, 159, 181, 144, 87, 114, 107, 87, 3, 116, 48, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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