Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebe9e4a0118d9536ef7917513eb766456b37ac0bda16dc702a757b328c9c9819

Tx prefix hash: 4cd34e0b59625a8f6306c3f821cab4175c465f0015201725848d069737d8155f
Tx public key: 6e80dddc7bf748a4bd90d3ea2ab5e0a46805fd5d480248a91c67693fb6de51f4
Timestamp: 1705194800 Timestamp [UCT]: 2024-01-14 01:13:20 Age [y:d:h:m:s]: 01:065:15:53:34
Block: 934793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308047 RingCT/type: yes/0
Extra: 016e80dddc7bf748a4bd90d3ea2ab5e0a46805fd5d480248a91c67693fb6de51f402110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1fcae84f1702b7b1e5e214655ae4282a1802992b92fddae9bd8942c3f263043 0.600000000000 1392809 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": 934803, "vin": [ { "gen": { "height": 934793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1fcae84f1702b7b1e5e214655ae4282a1802992b92fddae9bd8942c3f263043" } } ], "extra": [ 1, 110, 128, 221, 220, 123, 247, 72, 164, 189, 144, 211, 234, 42, 181, 224, 164, 104, 5, 253, 93, 72, 2, 72, 169, 28, 103, 105, 63, 182, 222, 81, 244, 2, 17, 0, 0, 0, 6, 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