Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f88cc1803a7a4c362f9db5be54151cf73191dd3afff9ca52123699c9714d959b

Tx prefix hash: 54066adb11d87772b4acd9afd28fae6ce89d080f1874a9b79db80d9da891379f
Tx public key: 65fe7bb921f8d962ad27c831d6702ed42d5321c5c59f095cfd2fa8470f678c85
Timestamp: 1710681023 Timestamp [UCT]: 2024-03-17 13:10:23 Age [y:d:h:m:s]: 01:231:14:47:32
Block: 980320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424212 RingCT/type: yes/0
Extra: 0165fe7bb921f8d962ad27c831d6702ed42d5321c5c59f095cfd2fa8470f678c8502110000001159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3a5d086fc32f25eedb2634f509a5df0a6c000a5245ab9a4f4e1f521215f7ebe 0.600000000000 1440385 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": 980330, "vin": [ { "gen": { "height": 980320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3a5d086fc32f25eedb2634f509a5df0a6c000a5245ab9a4f4e1f521215f7ebe" } } ], "extra": [ 1, 101, 254, 123, 185, 33, 248, 217, 98, 173, 39, 200, 49, 214, 112, 46, 212, 45, 83, 33, 197, 197, 159, 9, 92, 253, 47, 168, 71, 15, 103, 140, 133, 2, 17, 0, 0, 0, 17, 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