Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4acef9956bac99e31de53815a2ea680e87cf222fe8bb0bc3d0669a28d6f2d6c

Tx prefix hash: e1b9cc26cc6f73fa0685b5035bde45ca51d2801449abb5b8ecc9d682383416bf
Tx public key: bc004b3565976602296957c4993dfd21c25a7dc3dc312b3c5ffd8e731d9d8e68
Timestamp: 1714544452 Timestamp [UCT]: 2024-05-01 06:20:52 Age [y:d:h:m:s]: 00:346:12:38:38
Block: 1012329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247710 RingCT/type: yes/0
Extra: 01bc004b3565976602296957c4993dfd21c25a7dc3dc312b3c5ffd8e731d9d8e6802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3950e59f9d5a64a7215154704c09e394d0e08da978bdade8243ac3b3cfa872f5 0.600000000000 1474817 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": 1012339, "vin": [ { "gen": { "height": 1012329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3950e59f9d5a64a7215154704c09e394d0e08da978bdade8243ac3b3cfa872f5" } } ], "extra": [ 1, 188, 0, 75, 53, 101, 151, 102, 2, 41, 105, 87, 196, 153, 61, 253, 33, 194, 90, 125, 195, 220, 49, 43, 60, 95, 253, 142, 115, 29, 157, 142, 104, 2, 17, 0, 0, 0, 1, 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