Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4b10532b1559739765f1f344f1b94d9dd4cfc1c62c7aef6271c95dac5d62d03

Tx prefix hash: 03390d7f2bbf1339a5be3224d692b8d57e39c7a7661403ce42a2bc080e184dd5
Tx public key: cc2ae0c775f1d91d66ea27f106b3f43de77110d271891004cfec8c369a56d8b4
Timestamp: 1652859617 Timestamp [UCT]: 2022-05-18 07:40:17 Age [y:d:h:m:s]: 02:344:04:18:06
Block: 503445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 766406 RingCT/type: yes/0
Extra: 01cc2ae0c775f1d91d66ea27f106b3f43de77110d271891004cfec8c369a56d8b402110000000575e3f0e9000000000000000000

1 output(s) for total of 13.178862460000 dcy

stealth address amount amount idx
00: be2bb294557d356f74c13176e13d8d6aa4c1b0fac994ce0a6a08816a0fcd6345 13.178862460000 928514 of 0

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": 503455, "vin": [ { "gen": { "height": 503445 } } ], "vout": [ { "amount": 13178862460, "target": { "key": "be2bb294557d356f74c13176e13d8d6aa4c1b0fac994ce0a6a08816a0fcd6345" } } ], "extra": [ 1, 204, 42, 224, 199, 117, 241, 217, 29, 102, 234, 39, 241, 6, 179, 244, 61, 231, 113, 16, 210, 113, 137, 16, 4, 207, 236, 140, 54, 154, 86, 216, 180, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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