Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5526a4fbe54788f7131eb9e9d3b8b1244199cd85a8ede715d061d0362eba3989

Tx prefix hash: a72f43e94d2312244bf7ddd79a346a7d9fb233881a82ebb25ecacf8513a80393
Tx public key: 47edbfccbdf1a5d0b625fb9e38bf1c030b9f05bb2c989e405e9043826f84ea1d
Timestamp: 1579190525 Timestamp [UCT]: 2020-01-16 16:02:05 Age [y:d:h:m:s]: 05:036:20:47:23
Block: 46927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1176433 RingCT/type: yes/0
Extra: 0147edbfccbdf1a5d0b625fb9e38bf1c030b9f05bb2c989e405e9043826f84ea1d0211000000108a2ee0d9000000000000000000

1 output(s) for total of 429.054247949000 dcy

stealth address amount amount idx
00: 848ee6fda3c2ef078c5fef2f4fc2db76c6ee007b0ee050a2b5c8310437d914bc 429.054247949000 86567 of 0

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": 46937, "vin": [ { "gen": { "height": 46927 } } ], "vout": [ { "amount": 429054247949, "target": { "key": "848ee6fda3c2ef078c5fef2f4fc2db76c6ee007b0ee050a2b5c8310437d914bc" } } ], "extra": [ 1, 71, 237, 191, 204, 189, 241, 165, 208, 182, 37, 251, 158, 56, 191, 28, 3, 11, 159, 5, 187, 44, 152, 158, 64, 94, 144, 67, 130, 111, 132, 234, 29, 2, 17, 0, 0, 0, 16, 138, 46, 224, 217, 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