Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2c7d87753f2a03ea121ade163a690f080af4b1da61cee3a1b20ac1bcf746e22

Tx prefix hash: 9db8cc6d476a2dcbba8476499d1d4d8f84dd6e5bd3bea5745ec2a7d898537e77
Tx public key: c58dc46845358b4740b8377b126bbf685b74f4de294a45d346abc8228c80f664
Timestamp: 1701669937 Timestamp [UCT]: 2023-12-04 06:05:37 Age [y:d:h:m:s]: 01:340:07:57:05
Block: 905580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 502112 RingCT/type: yes/0
Extra: 01c58dc46845358b4740b8377b126bbf685b74f4de294a45d346abc8228c80f66402110000000575e3f0e9000000000000000000

1 output(s) for total of 0.612967588000 dcy

stealth address amount amount idx
00: 352b4901f739fac8baddd4d2f7eca5627a4aef53380fbbfd8eb5d10209364bae 0.612967588000 1362471 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": 905590, "vin": [ { "gen": { "height": 905580 } } ], "vout": [ { "amount": 612967588, "target": { "key": "352b4901f739fac8baddd4d2f7eca5627a4aef53380fbbfd8eb5d10209364bae" } } ], "extra": [ 1, 197, 141, 196, 104, 69, 53, 139, 71, 64, 184, 55, 123, 18, 107, 191, 104, 91, 116, 244, 222, 41, 74, 69, 211, 70, 171, 200, 34, 140, 128, 246, 100, 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