Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3599db01b03e16cca54bac7e16d654052ec6868f3393bde3afc69f2062ac66d2

Tx prefix hash: 901f6f0bdac5b1e420880edc0510d9f22e2847acc0ed10626dc86c4a563c4842
Tx public key: d09f2af865db940214887c0d08b32eec817b6b63378ee671e69d8cde8dc1c49f
Timestamp: 1721144759 Timestamp [UCT]: 2024-07-16 15:45:59 Age [y:d:h:m:s]: 00:130:16:15:11
Block: 1067059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93495 RingCT/type: yes/0
Extra: 01d09f2af865db940214887c0d08b32eec817b6b63378ee671e69d8cde8dc1c49f02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecb7451c20ca94e174c399cf2d5792a9d00f1ae4f9dcff39d39ae4c52bbe9fa5 0.600000000000 1537770 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": 1067069, "vin": [ { "gen": { "height": 1067059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecb7451c20ca94e174c399cf2d5792a9d00f1ae4f9dcff39d39ae4c52bbe9fa5" } } ], "extra": [ 1, 208, 159, 42, 248, 101, 219, 148, 2, 20, 136, 124, 13, 8, 179, 46, 236, 129, 123, 107, 99, 55, 142, 230, 113, 230, 157, 140, 222, 141, 193, 196, 159, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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