Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85b17bd9b562d2bdea69380f378712ea5a2460f8352697ed5033b976d12f5ad6

Tx prefix hash: 05fd4507af1bdd963ec82c1223406da3cb997bd3d177f498a5580741fe0d5830
Tx public key: 833a761c3c3a12ecc8ebb2f53d3abfe801f3122b73815dfdec59b5a08564042c
Timestamp: 1733628870 Timestamp [UCT]: 2024-12-08 03:34:30 Age [y:d:h:m:s]: 00:189:22:12:20
Block: 1170446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135471 RingCT/type: yes/0
Extra: 01833a761c3c3a12ecc8ebb2f53d3abfe801f3122b73815dfdec59b5a08564042c021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 980fb30321cc29f070c65b2a99c4eaa64c082c551eb1407c32f7550cdd684a7f 0.600000000000 1656177 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": 1170456, "vin": [ { "gen": { "height": 1170446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "980fb30321cc29f070c65b2a99c4eaa64c082c551eb1407c32f7550cdd684a7f" } } ], "extra": [ 1, 131, 58, 118, 28, 60, 58, 18, 236, 200, 235, 178, 245, 61, 58, 191, 232, 1, 243, 18, 43, 115, 129, 93, 253, 236, 89, 181, 160, 133, 100, 4, 44, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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