Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a075be9769fce97af91eb755135f4792b252dd25ad765f4a6c9caa2ac92c647

Tx prefix hash: 28c2ea64f74bfd1cc274db668e0f8c98d8fe200d666675bb996f1f0829b0afc6
Tx public key: a462896ded3cfdb3faf9d5db824e37c506d91c7948d244257b74128092c41edb
Timestamp: 1694037921 Timestamp [UCT]: 2023-09-06 22:05:21 Age [y:d:h:m:s]: 01:265:09:10:37
Block: 842501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450831 RingCT/type: yes/0
Extra: 01a462896ded3cfdb3faf9d5db824e37c506d91c7948d244257b74128092c41edb02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.991846616000 dcy

stealth address amount amount idx
00: 69c95160e4a12520f920e8cb1f889b9688337b55041507a69e6a59fd92d7fd53 0.991846616000 1295627 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": 842511, "vin": [ { "gen": { "height": 842501 } } ], "vout": [ { "amount": 991846616, "target": { "key": "69c95160e4a12520f920e8cb1f889b9688337b55041507a69e6a59fd92d7fd53" } } ], "extra": [ 1, 164, 98, 137, 109, 237, 60, 253, 179, 250, 249, 213, 219, 130, 78, 55, 197, 6, 217, 28, 121, 72, 210, 68, 37, 123, 116, 18, 128, 146, 196, 30, 219, 2, 17, 0, 0, 0, 7, 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