Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8dd430efca353df5b11d70b7c83e3b85a7421e0d3687deea7bf729435b08e4b

Tx prefix hash: c86b4008c0d9f99eda6d82147d34f2f42bc4352254a76700a5684ae4a40e8e1e
Tx public key: f1513fe6f6877b10e7a8b67db5c43d9ae0fee9b46d23d4b3110f889ed964149c
Timestamp: 1719002359 Timestamp [UCT]: 2024-06-21 20:39:19 Age [y:d:h:m:s]: 00:246:11:33:56
Block: 1049259 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176105 RingCT/type: yes/0
Extra: 01f1513fe6f6877b10e7a8b67db5c43d9ae0fee9b46d23d4b3110f889ed964149c02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b38c9f6a976e8f8742ac5f170ac773dd2e4c25e88e031e5ff148fc68dad5083f 0.600000000000 1519358 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": 1049269, "vin": [ { "gen": { "height": 1049259 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b38c9f6a976e8f8742ac5f170ac773dd2e4c25e88e031e5ff148fc68dad5083f" } } ], "extra": [ 1, 241, 81, 63, 230, 246, 135, 123, 16, 231, 168, 182, 125, 181, 196, 61, 154, 224, 254, 233, 180, 109, 35, 212, 179, 17, 15, 136, 158, 217, 100, 20, 156, 2, 17, 0, 0, 0, 6, 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