Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd8611eee716e59ec21aab0bfe9fcfa532d4639a2b78f276a46fc20adb3d4906

Tx prefix hash: 4bdf706a9ac9cdf2a8df3a52da8fd005d45b9f978ce6e5c2a0d32485499eb3aa
Tx public key: 247d187cd16b37b12c43e0ca735ff8cb657906baae6b924b28d5e0165d248d20
Timestamp: 1583856245 Timestamp [UCT]: 2020-03-10 16:04:05 Age [y:d:h:m:s]: 04:359:20:44:03
Block: 79926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152039 RingCT/type: yes/0
Extra: 01247d187cd16b37b12c43e0ca735ff8cb657906baae6b924b28d5e0165d248d20021100000002995a6b02000000000000000000

1 output(s) for total of 333.559084508000 dcy

stealth address amount amount idx
00: 2bda9c978826c8c11bfd8d7e7f135a26fe857a50e32856934e94409c5e23239d 333.559084508000 146244 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": 79936, "vin": [ { "gen": { "height": 79926 } } ], "vout": [ { "amount": 333559084508, "target": { "key": "2bda9c978826c8c11bfd8d7e7f135a26fe857a50e32856934e94409c5e23239d" } } ], "extra": [ 1, 36, 125, 24, 124, 209, 107, 55, 177, 44, 67, 224, 202, 115, 95, 248, 203, 101, 121, 6, 186, 174, 107, 146, 75, 40, 213, 224, 22, 93, 36, 141, 32, 2, 17, 0, 0, 0, 2, 153, 90, 107, 2, 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