Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e28535a69ba7efca63b664dcd014bf96635b15e9bfeea2b68cdfca0e14ac23bd

Tx prefix hash: 35fced5ede2b46e490d36dad1d84ddc1094ae7c92a5cae849542007a1e9405dc
Tx public key: 4ac27915d87b1fef3b755a1adfc9559a92e7adf34cd4138366078b2a5b4f08db
Timestamp: 1705575547 Timestamp [UCT]: 2024-01-18 10:59:07 Age [y:d:h:m:s]: 01:290:19:55:22
Block: 937953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466672 RingCT/type: yes/0
Extra: 014ac27915d87b1fef3b755a1adfc9559a92e7adf34cd4138366078b2a5b4f08db02110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c09b8ab5a9a7a0d8c39a57a516cc0338bb6351f8caca7cf448dd623a6303e0f5 0.600000000000 1396017 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": 937963, "vin": [ { "gen": { "height": 937953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c09b8ab5a9a7a0d8c39a57a516cc0338bb6351f8caca7cf448dd623a6303e0f5" } } ], "extra": [ 1, 74, 194, 121, 21, 216, 123, 31, 239, 59, 117, 90, 26, 223, 201, 85, 154, 146, 231, 173, 243, 76, 212, 19, 131, 102, 7, 139, 42, 91, 79, 8, 219, 2, 17, 0, 0, 0, 11, 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