Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5a14030a8236efb14e0ea73c698e07b4b474b4e40d34e0b23efb172fca710f3

Tx prefix hash: b4dde6c3e4088e1841c7069cab108cf3463738ced14011623fdb5de2f0e41ec4
Tx public key: 7c08c596f169fcc37db7dcb3a392f6ef33f5004c26c968bece03aa91240d38f4
Timestamp: 1726445339 Timestamp [UCT]: 2024-09-16 00:08:59 Age [y:d:h:m:s]: 00:184:10:03:15
Block: 1110991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131646 RingCT/type: yes/0
Extra: 017c08c596f169fcc37db7dcb3a392f6ef33f5004c26c968bece03aa91240d38f402110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de2b5397d2079ffdb5fd5e5f1b72af83d3a3767e14d40cc17f69e92ec4b9d567 0.600000000000 1589792 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": 1111001, "vin": [ { "gen": { "height": 1110991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de2b5397d2079ffdb5fd5e5f1b72af83d3a3767e14d40cc17f69e92ec4b9d567" } } ], "extra": [ 1, 124, 8, 197, 150, 241, 105, 252, 195, 125, 183, 220, 179, 163, 146, 246, 239, 51, 245, 0, 76, 38, 201, 104, 190, 206, 3, 170, 145, 36, 13, 56, 244, 2, 17, 0, 0, 0, 8, 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