Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84b137f622346578194630205c9a8992aabcb8cee26022674a2a28ec852530bf

Tx prefix hash: 5f8986da58abffbea9215ee3518dc43cca5773cebe2c5fb8e9570e0c4c86e440
Tx public key: aa8ae4ae68a36d9e6f4862702ef1eaef054d8ec1cbe5e30fe4e32e85e369f14a
Timestamp: 1725392331 Timestamp [UCT]: 2024-09-03 19:38:51 Age [y:d:h:m:s]: 00:212:05:01:04
Block: 1102265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151510 RingCT/type: yes/0
Extra: 01aa8ae4ae68a36d9e6f4862702ef1eaef054d8ec1cbe5e30fe4e32e85e369f14a02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e2f8e39af823f99013911b9a2730081cd001be7ba88d6502574572dde094b37 0.600000000000 1578632 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": 1102275, "vin": [ { "gen": { "height": 1102265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e2f8e39af823f99013911b9a2730081cd001be7ba88d6502574572dde094b37" } } ], "extra": [ 1, 170, 138, 228, 174, 104, 163, 109, 158, 111, 72, 98, 112, 46, 241, 234, 239, 5, 77, 142, 193, 203, 229, 227, 15, 228, 227, 46, 133, 227, 105, 241, 74, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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