Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb273a6aa115fa57c2667e84c6a33b6662b471b6a1caad4ae85beb9d8679f6d8

Tx prefix hash: 7a033345862aa04a0381852740e23d0e253b20e7e7d321ef47a88b74d555e1f2
Tx public key: e115ba74aa9b9cfb14d1277385fc8ccff34145e2097a87111b49de660e3aca85
Timestamp: 1722727824 Timestamp [UCT]: 2024-08-03 23:30:24 Age [y:d:h:m:s]: 00:247:13:37:50
Block: 1080169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176825 RingCT/type: yes/0
Extra: 01e115ba74aa9b9cfb14d1277385fc8ccff34145e2097a87111b49de660e3aca85021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae165ee6e1fede5f5fa1b9e0838f95b5237f0d3bba2e0f636d131f1a7f9444bc 0.600000000000 1553430 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": 1080179, "vin": [ { "gen": { "height": 1080169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae165ee6e1fede5f5fa1b9e0838f95b5237f0d3bba2e0f636d131f1a7f9444bc" } } ], "extra": [ 1, 225, 21, 186, 116, 170, 155, 156, 251, 20, 209, 39, 115, 133, 252, 140, 207, 243, 65, 69, 226, 9, 122, 135, 17, 27, 73, 222, 102, 14, 58, 202, 133, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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