Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e836fbf065c2c774f13f45c45800d3107244e9b4d633b8c9f445c183382d8d81

Tx prefix hash: 38256e314645f6cd2eaf5289984183a804da8b09a95089b9d3d158d201c2314e
Tx public key: ec138786fd71fc0e5baf7d0ed11102f5bca55444a4f45987069f58df184e3074
Timestamp: 1632433427 Timestamp [UCT]: 2021-09-23 21:43:47 Age [y:d:h:m:s]: 03:131:12:14:54
Block: 339678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 870026 RingCT/type: yes/0
Extra: 01ec138786fd71fc0e5baf7d0ed11102f5bca55444a4f45987069f58df184e30740211000000e536fe6557000000000000000000

1 output(s) for total of 45.973356390000 dcy

stealth address amount amount idx
00: a7f0cc08eee58368bb793e82d5d3b74e0faaa08814500a4c75fe7af9b1a45d96 45.973356390000 698509 of 0

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": 339688, "vin": [ { "gen": { "height": 339678 } } ], "vout": [ { "amount": 45973356390, "target": { "key": "a7f0cc08eee58368bb793e82d5d3b74e0faaa08814500a4c75fe7af9b1a45d96" } } ], "extra": [ 1, 236, 19, 135, 134, 253, 113, 252, 14, 91, 175, 125, 14, 209, 17, 2, 245, 188, 165, 84, 68, 164, 244, 89, 135, 6, 159, 88, 223, 24, 78, 48, 116, 2, 17, 0, 0, 0, 229, 54, 254, 101, 87, 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