Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 215d27036c077072b5786e72d111e2f7c8a897c1b58c53c6661215aa8b6ae3ef

Tx prefix hash: 4aec9180a5af0c2ed1b532db444568d47852b2289f9be060c9c4b224e33d37e1
Tx public key: 2bc45522fcd1241ab3ce5290bdd2c4b90bbba10e3d8430f200fd511458b88977
Timestamp: 1711714319 Timestamp [UCT]: 2024-03-29 12:11:59 Age [y:d:h:m:s]: 01:250:14:51:11
Block: 988883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437827 RingCT/type: yes/0
Extra: 012bc45522fcd1241ab3ce5290bdd2c4b90bbba10e3d8430f200fd511458b889770211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f9bdb08a1190f1277d3eb19c52dbb5cfdd463777d1f0a3003b68ac28923fbfb 0.600000000000 1449170 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": 988893, "vin": [ { "gen": { "height": 988883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f9bdb08a1190f1277d3eb19c52dbb5cfdd463777d1f0a3003b68ac28923fbfb" } } ], "extra": [ 1, 43, 196, 85, 34, 252, 209, 36, 26, 179, 206, 82, 144, 189, 210, 196, 185, 11, 187, 161, 14, 61, 132, 48, 242, 0, 253, 81, 20, 88, 184, 137, 119, 2, 17, 0, 0, 0, 5, 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