Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af18e6b89e0394d8d99cecee4ff3aa29d2b6865ab8ec3f384b80a6865a9e044b

Tx prefix hash: d9bb66aa75691066b651d3dc7ab995ab4e1887725f04f73e886e541798132d86
Tx public key: 63349ab8dd5fe0ea419b20f6e14b7da970fffe56c34c8f4c2b69205ad03425f4
Timestamp: 1721573810 Timestamp [UCT]: 2024-07-21 14:56:50 Age [y:d:h:m:s]: 00:247:21:14:13
Block: 1070600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177065 RingCT/type: yes/0
Extra: 0163349ab8dd5fe0ea419b20f6e14b7da970fffe56c34c8f4c2b69205ad03425f4021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebb20c7bfe3de8496dc03bfb72a0334ec3cc4738de776fe251256c2c63d9693d 0.600000000000 1542501 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": 1070610, "vin": [ { "gen": { "height": 1070600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebb20c7bfe3de8496dc03bfb72a0334ec3cc4738de776fe251256c2c63d9693d" } } ], "extra": [ 1, 99, 52, 154, 184, 221, 95, 224, 234, 65, 155, 32, 246, 225, 75, 125, 169, 112, 255, 254, 86, 195, 76, 143, 76, 43, 105, 32, 90, 208, 52, 37, 244, 2, 17, 0, 0, 0, 4, 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