Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eca2a44f93641b628cc0bc9abbf43515a40343ccd4ee33444f5d3de2981be641

Tx prefix hash: 11af9b3eb46604a551cc5f9c213ffae8e12283ed76a82785a67951899e4c9233
Tx public key: 713f4e4e8cd495eb8d3834a48f24fdd654d503ea43e862b4502db0b1f317b404
Timestamp: 1677108862 Timestamp [UCT]: 2023-02-22 23:34:22 Age [y:d:h:m:s]: 02:044:19:34:10
Block: 702850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 553607 RingCT/type: yes/0
Extra: 01713f4e4e8cd495eb8d3834a48f24fdd654d503ea43e862b4502db0b1f317b40402110000000274b6d784000000000000000000

1 output(s) for total of 2.878499061000 dcy

stealth address amount amount idx
00: efa69b9f6989862c1c1fb2dea5d2a5e34b216e1e8e50d9daf1c69cd34d5f2cfa 2.878499061000 1146403 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": 702860, "vin": [ { "gen": { "height": 702850 } } ], "vout": [ { "amount": 2878499061, "target": { "key": "efa69b9f6989862c1c1fb2dea5d2a5e34b216e1e8e50d9daf1c69cd34d5f2cfa" } } ], "extra": [ 1, 113, 63, 78, 78, 140, 212, 149, 235, 141, 56, 52, 164, 143, 36, 253, 214, 84, 213, 3, 234, 67, 232, 98, 180, 80, 45, 176, 177, 243, 23, 180, 4, 2, 17, 0, 0, 0, 2, 116, 182, 215, 132, 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