Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aab3bc005075e98a37e37cba0a635e1ddba8a60d212c4de718b619e92b20238c

Tx prefix hash: 30d7b4dbb8645462d5301f7d087a39e2de97f1a5938acc21def0c0d7d144aa67
Tx public key: c5372f0a63e8028cd4979c42da942b4d5717cd1941bfed50b66af51a5b711955
Timestamp: 1712497679 Timestamp [UCT]: 2024-04-07 13:47:59 Age [y:d:h:m:s]: 00:324:07:11:30
Block: 995330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231862 RingCT/type: yes/0
Extra: 01c5372f0a63e8028cd4979c42da942b4d5717cd1941bfed50b66af51a5b71195502110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79475c975d61f354370d3b8eabb3289b41ad10c5ce674a8a59d6f96d10a2129b 0.600000000000 1455736 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": 995340, "vin": [ { "gen": { "height": 995330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79475c975d61f354370d3b8eabb3289b41ad10c5ce674a8a59d6f96d10a2129b" } } ], "extra": [ 1, 197, 55, 47, 10, 99, 232, 2, 140, 212, 151, 156, 66, 218, 148, 43, 77, 87, 23, 205, 25, 65, 191, 237, 80, 182, 106, 245, 26, 91, 113, 25, 85, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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