Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 042d0bb7c80210b40dc07c98e7500ec8f10e3d03a469ad3374d758ccffd274d7

Tx prefix hash: c49ac85e1723bc66edeb3a1d33bea6d9294cb8d2fe0266c28774701a1c4fed5f
Tx public key: 12a3ed5be0a897cd24e75ccf88e531be336555f7aee5f0e14cea43162368f8c4
Timestamp: 1737962462 Timestamp [UCT]: 2025-01-27 07:21:02 Age [y:d:h:m:s]: 00:141:23:22:18
Block: 1206091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101382 RingCT/type: yes/0
Extra: 0112a3ed5be0a897cd24e75ccf88e531be336555f7aee5f0e14cea43162368f8c4021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d757a42f1920c0aefc41610dc3ec4f0c1491e54c27436f28081b431c833c3ed4 0.600000000000 1692792 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": 1206101, "vin": [ { "gen": { "height": 1206091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d757a42f1920c0aefc41610dc3ec4f0c1491e54c27436f28081b431c833c3ed4" } } ], "extra": [ 1, 18, 163, 237, 91, 224, 168, 151, 205, 36, 231, 92, 207, 136, 229, 49, 190, 51, 101, 85, 247, 174, 229, 240, 225, 76, 234, 67, 22, 35, 104, 248, 196, 2, 17, 0, 0, 0, 3, 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