Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23c2f14f68b4d5d9b05d208ede33bb536d29312d9246fe0f5a117300d8f01c6b

Tx prefix hash: e2db391b4f49df2ede3b20d7a4a52cfb93d6453c2ff82f8343cca1575a75da9e
Tx public key: e73ac53f3a0d814748e085666924a8888d99cc2e853a2318cba34a257b4792d6
Timestamp: 1707031975 Timestamp [UCT]: 2024-02-04 07:32:55 Age [y:d:h:m:s]: 00:346:15:07:12
Block: 950029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248153 RingCT/type: yes/0
Extra: 01e73ac53f3a0d814748e085666924a8888d99cc2e853a2318cba34a257b4792d602110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 885bfdb3563d4e5cc46b8f944db371addf6b27179e1f81c2447c7e367aa70877 0.600000000000 1408577 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": 950039, "vin": [ { "gen": { "height": 950029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "885bfdb3563d4e5cc46b8f944db371addf6b27179e1f81c2447c7e367aa70877" } } ], "extra": [ 1, 231, 58, 197, 63, 58, 13, 129, 71, 72, 224, 133, 102, 105, 36, 168, 136, 141, 153, 204, 46, 133, 58, 35, 24, 203, 163, 74, 37, 123, 71, 146, 214, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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