Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 735fe5198ec71134f885345adc6799dd4fb190c38fb1f954188c2e28db925b18

Tx prefix hash: 5ef73bfaa059dacfd5472a9e22b7e559fff5c0ee4761a823a7ad523f49b17378
Tx public key: 1300893fbde88a32cb71683f7ddb75c458d2ae930f0e1ec635ab8061925b2d02
Timestamp: 1710181482 Timestamp [UCT]: 2024-03-11 18:24:42 Age [y:d:h:m:s]: 00:348:22:17:33
Block: 976165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249458 RingCT/type: yes/0
Extra: 011300893fbde88a32cb71683f7ddb75c458d2ae930f0e1ec635ab8061925b2d020211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f54b1203a6d6048cc876d588fd5e4bf2068b6ac1d890fe19069aad369255f34b 0.600000000000 1436156 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": 976175, "vin": [ { "gen": { "height": 976165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f54b1203a6d6048cc876d588fd5e4bf2068b6ac1d890fe19069aad369255f34b" } } ], "extra": [ 1, 19, 0, 137, 63, 189, 232, 138, 50, 203, 113, 104, 63, 125, 219, 117, 196, 88, 210, 174, 147, 15, 14, 30, 198, 53, 171, 128, 97, 146, 91, 45, 2, 2, 17, 0, 0, 0, 4, 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