Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fc192bf749d3487bd8ccd3525053863bc92a74dd5c768467fabb9a98532c1dc

Tx prefix hash: cdadac9fb8b2bf46816e3753d6f60df1ff7486c599103d9ba44b8af2c6f4bb21
Tx public key: bd49ae5806c7b00aeb140523a2341e9f2885a0535f13a865fec57814b0c41037
Timestamp: 1716253755 Timestamp [UCT]: 2024-05-21 01:09:15 Age [y:d:h:m:s]: 01:026:10:28:54
Block: 1026509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279701 RingCT/type: yes/0
Extra: 01bd49ae5806c7b00aeb140523a2341e9f2885a0535f13a865fec57814b0c4103702110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c031618e076c7a3b2bcc74a27322d6e6908af0ae5a44b56ff7e6adb12d9ca2e1 0.600000000000 1493628 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": 1026519, "vin": [ { "gen": { "height": 1026509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c031618e076c7a3b2bcc74a27322d6e6908af0ae5a44b56ff7e6adb12d9ca2e1" } } ], "extra": [ 1, 189, 73, 174, 88, 6, 199, 176, 10, 235, 20, 5, 35, 162, 52, 30, 159, 40, 133, 160, 83, 95, 19, 168, 101, 254, 197, 120, 20, 176, 196, 16, 55, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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