Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1724391674828b5f3433aa10bb2c4149c494ec9dd782e2254ce398dfd1397c59

Tx prefix hash: cc782f0f89b49d5b906aa9a9ddfbb02f51b27138e3f2e9c26679391c0bfc507e
Tx public key: fe82727e4137beab0413b389c5cdd8bc0fec46c6baf772f8daa6ca72bba4c5f7
Timestamp: 1713182244 Timestamp [UCT]: 2024-04-15 11:57:24 Age [y:d:h:m:s]: 00:232:21:19:05
Block: 1001029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166718 RingCT/type: yes/0
Extra: 01fe82727e4137beab0413b389c5cdd8bc0fec46c6baf772f8daa6ca72bba4c5f702110000000e59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f544e10fa390bc339826110c59ee3ebd1b5940d4fafe5f360da6e118c1f1b3c7 0.600000000000 1461531 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": 1001039, "vin": [ { "gen": { "height": 1001029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f544e10fa390bc339826110c59ee3ebd1b5940d4fafe5f360da6e118c1f1b3c7" } } ], "extra": [ 1, 254, 130, 114, 126, 65, 55, 190, 171, 4, 19, 179, 137, 197, 205, 216, 188, 15, 236, 70, 198, 186, 247, 114, 248, 218, 166, 202, 114, 187, 164, 197, 247, 2, 17, 0, 0, 0, 14, 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