Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f46649441906c2ed1332da7025954fe78e98f044d01a3998dbf2ffdc6b30a67

Tx prefix hash: eaa0aa9f4c1917acac3ef55fec9e7652b7fdd49bd404d55644dcf75aa9e1967f
Tx public key: 4fa6bd530174fba63075a9b2f55eb1a4bf465c84d514fec5cf74c5539cdb5f5d
Timestamp: 1687124021 Timestamp [UCT]: 2023-06-18 21:33:41 Age [y:d:h:m:s]: 01:348:14:17:26
Block: 785250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 510356 RingCT/type: yes/0
Extra: 014fa6bd530174fba63075a9b2f55eb1a4bf465c84d514fec5cf74c5539cdb5f5d0211000000014b8f5122000000000000000000

1 output(s) for total of 1.535155047000 dcy

stealth address amount amount idx
00: b4f2631d213ca1785d3c403603f7e093d2441beba491a504e221b79b1630b1bc 1.535155047000 1235195 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": 785260, "vin": [ { "gen": { "height": 785250 } } ], "vout": [ { "amount": 1535155047, "target": { "key": "b4f2631d213ca1785d3c403603f7e093d2441beba491a504e221b79b1630b1bc" } } ], "extra": [ 1, 79, 166, 189, 83, 1, 116, 251, 166, 48, 117, 169, 178, 245, 94, 177, 164, 191, 70, 92, 132, 213, 20, 254, 197, 207, 116, 197, 83, 156, 219, 95, 93, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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