Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c0f683e2be12771ee17b785941cb14032f15c9758aa16ddaa82d1f7fe781e4e

Tx prefix hash: c99656404d73ea03c09a56f54c9c4c2e1384e96a070d86628db10df4f6eeb9f6
Tx public key: 0d419d5189917cda460defa022811f90cdf8b03284c136574a0d7e5c34dcc8b7
Timestamp: 1673859123 Timestamp [UCT]: 2023-01-16 08:52:03 Age [y:d:h:m:s]: 02:002:05:05:58
Block: 675878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523478 RingCT/type: yes/0
Extra: 010d419d5189917cda460defa022811f90cdf8b03284c136574a0d7e5c34dcc8b70211000000035029cbac000000000000000000

1 output(s) for total of 3.536189777000 dcy

stealth address amount amount idx
00: be34a645b844d87807fd7c2cdbb7905ecf47931370b2cf13329d5e55a8f1ce64 3.536189777000 1117565 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": 675888, "vin": [ { "gen": { "height": 675878 } } ], "vout": [ { "amount": 3536189777, "target": { "key": "be34a645b844d87807fd7c2cdbb7905ecf47931370b2cf13329d5e55a8f1ce64" } } ], "extra": [ 1, 13, 65, 157, 81, 137, 145, 124, 218, 70, 13, 239, 160, 34, 129, 31, 144, 205, 248, 176, 50, 132, 193, 54, 87, 74, 13, 126, 92, 52, 220, 200, 183, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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