Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf74c5ffa75834dfe0d81b45fe29e341cb6b49c2b7be962d200642aab1c1fb46

Tx prefix hash: 73943b8aa5f5167029a7b9df34cc3851ba987b437b88824d92e82fcecf54762c
Tx public key: 3c4cbedd3e221cfa618c398c1500af9737061a3ba5553192f6f05a4f9962293b
Timestamp: 1723288275 Timestamp [UCT]: 2024-08-10 11:11:15 Age [y:d:h:m:s]: 00:220:23:49:59
Block: 1084824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157837 RingCT/type: yes/0
Extra: 013c4cbedd3e221cfa618c398c1500af9737061a3ba5553192f6f05a4f9962293b021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66d361ea51b184c0ff81969eeb2b2f43c8032d9d36280fc625f4b0426e4d99fd 0.600000000000 1559239 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": 1084834, "vin": [ { "gen": { "height": 1084824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66d361ea51b184c0ff81969eeb2b2f43c8032d9d36280fc625f4b0426e4d99fd" } } ], "extra": [ 1, 60, 76, 190, 221, 62, 34, 28, 250, 97, 140, 57, 140, 21, 0, 175, 151, 55, 6, 26, 59, 165, 85, 49, 146, 246, 240, 90, 79, 153, 98, 41, 59, 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