Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f253431df1a8f22785f9dfcd93bc81870e247e1a8e96fc75e16989c86c773449

Tx prefix hash: 1963f1272f72650969c4ab159fd9e71197b86541a86c18c5a53b7bbcb2c89ff6
Tx public key: bd465a81f7e7b136e60db0f1984965a711156abc99576c4e85f4e3aa29e95061
Timestamp: 1724737857 Timestamp [UCT]: 2024-08-27 05:50:57 Age [y:d:h:m:s]: 00:220:13:37:18
Block: 1096822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157507 RingCT/type: yes/0
Extra: 01bd465a81f7e7b136e60db0f1984965a711156abc99576c4e85f4e3aa29e95061021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91c0771589b3783af2a9075a1862c08928a8927cb2d0c1f2e7d0cb0f19a50f3a 0.600000000000 1572017 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": 1096832, "vin": [ { "gen": { "height": 1096822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91c0771589b3783af2a9075a1862c08928a8927cb2d0c1f2e7d0cb0f19a50f3a" } } ], "extra": [ 1, 189, 70, 90, 129, 247, 231, 177, 54, 230, 13, 176, 241, 152, 73, 101, 167, 17, 21, 106, 188, 153, 87, 108, 78, 133, 244, 227, 170, 41, 233, 80, 97, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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