Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8a0d7cc2a2755fead45c1dc7d7cf792f23194eb54961ff86a34a5568ce8d57d

Tx prefix hash: 197643074ca1be3f5747e34d673ad8e64bb3ff9cd6037aedce8c79fe5318fbcd
Tx public key: b0b5e0a741afc501291dd6781c83b6a42b529e7787f674d50d5644e0a4ca1758
Timestamp: 1720686944 Timestamp [UCT]: 2024-07-11 08:35:44 Age [y:d:h:m:s]: 00:286:13:50:13
Block: 1063262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204738 RingCT/type: yes/0
Extra: 01b0b5e0a741afc501291dd6781c83b6a42b529e7787f674d50d5644e0a4ca1758021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23082aaa8cfda3ac079438c3e46c92e462abf0132d280d884703a095a2cd26fa 0.600000000000 1533777 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": 1063272, "vin": [ { "gen": { "height": 1063262 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23082aaa8cfda3ac079438c3e46c92e462abf0132d280d884703a095a2cd26fa" } } ], "extra": [ 1, 176, 181, 224, 167, 65, 175, 197, 1, 41, 29, 214, 120, 28, 131, 182, 164, 43, 82, 158, 119, 135, 246, 116, 213, 13, 86, 68, 224, 164, 202, 23, 88, 2, 17, 0, 0, 0, 5, 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