Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d072cbeaf16fab95c2473196f48024ed298c9887d3a65f8c3eca383b5ea48f38

Tx prefix hash: 87bb7ab6e6a757f5e64c311eddebf10ea99ae7aaec700f8622261820c847e192
Tx public key: 91312c6401fb2d4e3f9448b069f532971e92787757c687a46a11ead2a644405a
Timestamp: 1712472867 Timestamp [UCT]: 2024-04-07 06:54:27 Age [y:d:h:m:s]: 01:069:12:02:38
Block: 995118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310609 RingCT/type: yes/0
Extra: 0191312c6401fb2d4e3f9448b069f532971e92787757c687a46a11ead2a644405a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93f156da6b4c6ffb183f5bfea3940bb67219803fe5ed4a1beea981d3b161d58b 0.600000000000 1455522 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": 995128, "vin": [ { "gen": { "height": 995118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93f156da6b4c6ffb183f5bfea3940bb67219803fe5ed4a1beea981d3b161d58b" } } ], "extra": [ 1, 145, 49, 44, 100, 1, 251, 45, 78, 63, 148, 72, 176, 105, 245, 50, 151, 30, 146, 120, 119, 87, 198, 135, 164, 106, 17, 234, 210, 166, 68, 64, 90, 2, 17, 0, 0, 0, 1, 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