Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ede79f445b462e7fdd33ef958fd452514f29a3f5f289388c8f6d296dc89088a5

Tx prefix hash: bd5c88487b22414659d5c74bd8a407678efdfc82a0d6da2e3980f61d5d2ed220
Tx public key: a9639b8abc0e4e14cf176534d8ecc501fc2a4a2633eaad45094ac29d1ae9a574
Timestamp: 1750762281 Timestamp [UCT]: 2025-06-24 10:51:21 Age [y:d:h:m:s]: 00:145:08:37:02
Block: 1311759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101824 RingCT/type: yes/0
Extra: 01a9639b8abc0e4e14cf176534d8ecc501fc2a4a2633eaad45094ac29d1ae9a57402110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fab3738a7b2505c1f1b7bddd52a14441cfeebf25bf6c51cdec76669acec3ff16 0.600000000000 1799388 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": 1311769, "vin": [ { "gen": { "height": 1311759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fab3738a7b2505c1f1b7bddd52a14441cfeebf25bf6c51cdec76669acec3ff16" } } ], "extra": [ 1, 169, 99, 155, 138, 188, 14, 78, 20, 207, 23, 101, 52, 216, 236, 197, 1, 252, 42, 74, 38, 51, 234, 173, 69, 9, 74, 194, 157, 26, 233, 165, 116, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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