Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 074f697d846dec89b3129272bab0813a7729617754accacf29e72428fe0f27f8

Tx prefix hash: efb6df86634a06d1792f2234c8ed2285d0bd3fef04cbf4d9cf5a3ae679617829
Tx public key: 157b48a049154538c5437a7459a3a72940b6d823193c2355f835252e2d8c5d57
Timestamp: 1703671854 Timestamp [UCT]: 2023-12-27 10:10:54 Age [y:d:h:m:s]: 01:113:05:27:21
Block: 922190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342048 RingCT/type: yes/0
Extra: 01157b48a049154538c5437a7459a3a72940b6d823193c2355f835252e2d8c5d5702110000000f7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de0b0e3b4869aa52351ee9f4ea16707528bf55b245d71cb91e4e2c2311e23adb 0.600000000000 1379884 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": 922200, "vin": [ { "gen": { "height": 922190 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de0b0e3b4869aa52351ee9f4ea16707528bf55b245d71cb91e4e2c2311e23adb" } } ], "extra": [ 1, 21, 123, 72, 160, 73, 21, 69, 56, 197, 67, 122, 116, 89, 163, 167, 41, 64, 182, 216, 35, 25, 60, 35, 85, 248, 53, 37, 46, 45, 140, 93, 87, 2, 17, 0, 0, 0, 15, 122, 156, 244, 199, 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