Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d579b652bb14c6a5b88a1c7460b7b8e3cb0d246bf1e4622a8889a7109a6ef406

Tx prefix hash: 317f43f3630e955156fa73db1a84cacdc932313f3b954d2746c59aaf77f390ca
Tx public key: 29cf0957344861546c75409cc56afedc9fb2cf8a7b18be938c9ac49ef1d908aa
Timestamp: 1709974867 Timestamp [UCT]: 2024-03-09 09:01:07 Age [y:d:h:m:s]: 00:311:17:49:03
Block: 974449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223151 RingCT/type: yes/0
Extra: 0129cf0957344861546c75409cc56afedc9fb2cf8a7b18be938c9ac49ef1d908aa0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a84923af8afcf3a8e93c2fb0fe8c908a8cfc7649e9ac7582a8d863590d7aecd 0.600000000000 1434404 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": 974459, "vin": [ { "gen": { "height": 974449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a84923af8afcf3a8e93c2fb0fe8c908a8cfc7649e9ac7582a8d863590d7aecd" } } ], "extra": [ 1, 41, 207, 9, 87, 52, 72, 97, 84, 108, 117, 64, 156, 197, 106, 254, 220, 159, 178, 207, 138, 123, 24, 190, 147, 140, 154, 196, 158, 241, 217, 8, 170, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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