Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b618fa0fe6dce4ccadfef75f8b22e653fe7a2df2212d9b4580d73106239a349

Tx prefix hash: e3a3bdb3a72ffb10d733faa4fbf66469f33ab1129f996dd5ec79e2fc6d69b954
Tx public key: 0cf9357f11b436c74b9c272d140d4e64cfdef5cfde9d19344533cf291f7b1866
Timestamp: 1745751180 Timestamp [UCT]: 2025-04-27 10:53:00 Age [y:d:h:m:s]: 00:248:21:30:57
Block: 1270533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175662 RingCT/type: yes/0
Extra: 010cf9357f11b436c74b9c272d140d4e64cfdef5cfde9d19344533cf291f7b18660211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be20bd1ca0107c68ac689bd3de3eeb99b84b1c9d1eb8839c6027aeb18cd67121 0.600000000000 1757776 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": 1270543, "vin": [ { "gen": { "height": 1270533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be20bd1ca0107c68ac689bd3de3eeb99b84b1c9d1eb8839c6027aeb18cd67121" } } ], "extra": [ 1, 12, 249, 53, 127, 17, 180, 54, 199, 75, 156, 39, 45, 20, 13, 78, 100, 207, 222, 245, 207, 222, 157, 25, 52, 69, 51, 207, 41, 31, 123, 24, 102, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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