Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58d4c554bad43c85d9b288fe612e050a6f5d323e2d85c1821cb2d114a3ba7fd7

Tx prefix hash: ddafe66ae183d8928ec7da6061b5bca1ae1beeaf88fcdcb67ccad83471ba7a33
Tx public key: 0d69d23e62e98cf62405270e2f17a007e9632b42d9f0acf8b77e68b4a55fd6ec
Timestamp: 1638366358 Timestamp [UCT]: 2021-12-01 13:45:58 Age [y:d:h:m:s]: 02:364:07:46:09
Block: 386128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 778407 RingCT/type: yes/0
Extra: 010d69d23e62e98cf62405270e2f17a007e9632b42d9f0acf8b77e68b4a55fd6ec021100000001f6cc1430000000000000000000

1 output(s) for total of 32.255072202000 dcy

stealth address amount amount idx
00: d1b5ff65aa778ee2b8df873ad2b83b364b51312bcf451b9f20f44ab183774089 32.255072202000 779073 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": 386138, "vin": [ { "gen": { "height": 386128 } } ], "vout": [ { "amount": 32255072202, "target": { "key": "d1b5ff65aa778ee2b8df873ad2b83b364b51312bcf451b9f20f44ab183774089" } } ], "extra": [ 1, 13, 105, 210, 62, 98, 233, 140, 246, 36, 5, 39, 14, 47, 23, 160, 7, 233, 99, 43, 66, 217, 240, 172, 248, 183, 126, 104, 180, 165, 95, 214, 236, 2, 17, 0, 0, 0, 1, 246, 204, 20, 48, 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