Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 596fd8d5eac6b1359950eebe58f97b4213283c396b6575f6b024c7e3b38a72bb

Tx prefix hash: 2f702533f647cfd49532bc3fa14b074b555044e38339f99dc758d6a4dfa238a7
Tx public key: 93130b12ddf869d0b5e8e2e87a8e534d79b30cf28856f639c78d4b06e9c78635
Timestamp: 1703292732 Timestamp [UCT]: 2023-12-23 00:52:12 Age [y:d:h:m:s]: 01:110:22:06:36
Block: 919043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340406 RingCT/type: yes/0
Extra: 0193130b12ddf869d0b5e8e2e87a8e534d79b30cf28856f639c78d4b06e9c786350211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a22de6482d3d77c4304d8604633319d137d15d7b49e6a734bc66f006e412ce2 0.600000000000 1376707 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": 919053, "vin": [ { "gen": { "height": 919043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a22de6482d3d77c4304d8604633319d137d15d7b49e6a734bc66f006e412ce2" } } ], "extra": [ 1, 147, 19, 11, 18, 221, 248, 105, 208, 181, 232, 226, 232, 122, 142, 83, 77, 121, 179, 12, 242, 136, 86, 246, 57, 199, 141, 75, 6, 233, 199, 134, 53, 2, 17, 0, 0, 0, 2, 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