Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f385baead801be1c697eb7ca930039c952915a3f74b30190ec443c49c6f0a9d4

Tx prefix hash: cf96b3a01a946450bfa06646823b7899bc05eead9e89778ef04a5b2848c2ced5
Tx public key: 52a2f2cc714a4e7ea4d342cde196c9285cbac1a597f8b37be665510a416b034b
Timestamp: 1723791625 Timestamp [UCT]: 2024-08-16 07:00:25 Age [y:d:h:m:s]: 00:163:02:53:04
Block: 1088986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116648 RingCT/type: yes/0
Extra: 0152a2f2cc714a4e7ea4d342cde196c9285cbac1a597f8b37be665510a416b034b021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39cfb45ea8f9922d457562ff82edc927794084f550c004c34f8498d1cf8b21ee 0.600000000000 1563605 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": 1088996, "vin": [ { "gen": { "height": 1088986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39cfb45ea8f9922d457562ff82edc927794084f550c004c34f8498d1cf8b21ee" } } ], "extra": [ 1, 82, 162, 242, 204, 113, 74, 78, 126, 164, 211, 66, 205, 225, 150, 201, 40, 92, 186, 193, 165, 151, 248, 179, 123, 230, 101, 81, 10, 65, 107, 3, 75, 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