Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00ca925e68a6f6da3f2b22362cccf88b9e4baff92bb8b454e3f325e8f97df190

Tx prefix hash: 189f511209161a728eb1ffa863a2ee7ad322261287a78adb51f5b50d441a0ae7
Tx public key: cd5eda87534cbf01368a9d841b24f8888ccc74c986cf7ddfcaf21a5d97791d5a
Timestamp: 1727026850 Timestamp [UCT]: 2024-09-22 17:40:50 Age [y:d:h:m:s]: 00:107:03:14:39
Block: 1115816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76599 RingCT/type: yes/0
Extra: 01cd5eda87534cbf01368a9d841b24f8888ccc74c986cf7ddfcaf21a5d97791d5a02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 370d13a19a1fafd2f0bd22b4f72525a912f9ee861916d7fc11ce1b5b7dd21766 0.600000000000 1596077 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": 1115826, "vin": [ { "gen": { "height": 1115816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "370d13a19a1fafd2f0bd22b4f72525a912f9ee861916d7fc11ce1b5b7dd21766" } } ], "extra": [ 1, 205, 94, 218, 135, 83, 76, 191, 1, 54, 138, 157, 132, 27, 36, 248, 136, 140, 204, 116, 201, 134, 207, 125, 223, 202, 242, 26, 93, 151, 121, 29, 90, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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