Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 049ebe35a8012b5fa0469339217cdba821fe8c1a3fb401cde8193b273f74cfab

Tx prefix hash: 370bb01fe6e48617466b929448089f0ae55e42e0fb1d88c29eb7efbed5997f73
Tx public key: d1c5124c4ff1d8fd1ccf07ad4d562247b26fa4da0c360902e5bcbda98ac594a4
Timestamp: 1713597959 Timestamp [UCT]: 2024-04-20 07:25:59 Age [y:d:h:m:s]: 00:361:22:02:46
Block: 1004456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258747 RingCT/type: yes/0
Extra: 01d1c5124c4ff1d8fd1ccf07ad4d562247b26fa4da0c360902e5bcbda98ac594a40211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d70e47582b52fa7a50c89680cd42b0e64bf885d3d5be4ea75e459dc7ba0075c 0.600000000000 1465024 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": 1004466, "vin": [ { "gen": { "height": 1004456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d70e47582b52fa7a50c89680cd42b0e64bf885d3d5be4ea75e459dc7ba0075c" } } ], "extra": [ 1, 209, 197, 18, 76, 79, 241, 216, 253, 28, 207, 7, 173, 77, 86, 34, 71, 178, 111, 164, 218, 12, 54, 9, 2, 229, 188, 189, 169, 138, 197, 148, 164, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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