Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9169e96d0099d72bec9365d0bc0eb29f27b57801f6a89dc590f6035e3cde548e

Tx prefix hash: 634a2389ee2b42334f6b9585ac17f3758f4e57c9bb54890aefe8a9d8f9725e79
Tx public key: 81c3ac5a427191e2e05fee82c6a550418fa4ab39cce975cb4d26d2ebfb3c358d
Timestamp: 1711137759 Timestamp [UCT]: 2024-03-22 20:02:39 Age [y:d:h:m:s]: 00:361:15:36:18
Block: 984104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258571 RingCT/type: yes/0
Extra: 0181c3ac5a427191e2e05fee82c6a550418fa4ab39cce975cb4d26d2ebfb3c358d0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f51f859b49bd91e0daccbb799dfcdb0ac435f776a557ba94fbcc7269252aea6 0.600000000000 1444259 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": 984114, "vin": [ { "gen": { "height": 984104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f51f859b49bd91e0daccbb799dfcdb0ac435f776a557ba94fbcc7269252aea6" } } ], "extra": [ 1, 129, 195, 172, 90, 66, 113, 145, 226, 224, 95, 238, 130, 198, 165, 80, 65, 143, 164, 171, 57, 204, 233, 117, 203, 77, 38, 210, 235, 251, 60, 53, 141, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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