Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae49937fd32758ca659153b5c4b63215240e27fff5bc5318d8b3e949da063d8f

Tx prefix hash: 78045472cbaac16368ae306bed3e1ab6d47d750b0c08375e7a7cad9b3200742c
Tx public key: 3d02e21d5c4aa18aafbe482374a47c0016679d75d4431f7e54c7fac838319791
Timestamp: 1714466005 Timestamp [UCT]: 2024-04-30 08:33:25 Age [y:d:h:m:s]: 00:198:18:24:22
Block: 1011671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142277 RingCT/type: yes/0
Extra: 013d02e21d5c4aa18aafbe482374a47c0016679d75d4431f7e54c7fac83831979102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e54f0e7bffb40ee705f137fe0212d2d541f12fd3bfb70d61d7bd320501c3d3a 0.600000000000 1473961 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": 1011681, "vin": [ { "gen": { "height": 1011671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e54f0e7bffb40ee705f137fe0212d2d541f12fd3bfb70d61d7bd320501c3d3a" } } ], "extra": [ 1, 61, 2, 226, 29, 92, 74, 161, 138, 175, 190, 72, 35, 116, 164, 124, 0, 22, 103, 157, 117, 212, 67, 31, 126, 84, 199, 250, 200, 56, 49, 151, 145, 2, 17, 0, 0, 0, 2, 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