Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d4f3b1162e5425c089abfed555879369e701c482eb74b8b04f005d7bd9255fd

Tx prefix hash: d34eed3ee4181bd92733e491975389243f1a1a0d08f03ad9020af1ea2764dab7
Tx public key: 7355f1259b51202b924c2ae6934775adc2c29f3ccae73cf26c234b524cc8965c
Timestamp: 1725659403 Timestamp [UCT]: 2024-09-06 21:50:03 Age [y:d:h:m:s]: 00:222:14:22:00
Block: 1104473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158939 RingCT/type: yes/0
Extra: 017355f1259b51202b924c2ae6934775adc2c29f3ccae73cf26c234b524cc8965c021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8b8b5a3b640ceedb46236021d3e6750d2d840a1d7baa0a23bc8f97f3ef9c145 0.600000000000 1581626 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": 1104483, "vin": [ { "gen": { "height": 1104473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8b8b5a3b640ceedb46236021d3e6750d2d840a1d7baa0a23bc8f97f3ef9c145" } } ], "extra": [ 1, 115, 85, 241, 37, 155, 81, 32, 43, 146, 76, 42, 230, 147, 71, 117, 173, 194, 194, 159, 60, 202, 231, 60, 242, 108, 35, 75, 82, 76, 200, 150, 92, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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