Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe56c034f535546d1d87f5fb7035a1b05957c665548625b2caf1bf8e209c647d

Tx prefix hash: d1b7e7da1880c6004c65da707be9c66a0d2385571748cf84c4a6067a65d6fd5c
Tx public key: 0c759e88e6d486b9d4a1d6c2ed3bd356721c7f3d099aa456baa3b1a911087920
Timestamp: 1695916897 Timestamp [UCT]: 2023-09-28 16:01:37 Age [y:d:h:m:s]: 01:181:12:57:43
Block: 858100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390792 RingCT/type: yes/0
Extra: 010c759e88e6d486b9d4a1d6c2ed3bd356721c7f3d099aa456baa3b1a9110879200211000000064b8f5122000000000000000000

1 output(s) for total of 0.880559142000 dcy

stealth address amount amount idx
00: 233c7f514438059262250ab42a032451a43c1f2a9c36717102edb1c67ad7a509 0.880559142000 1312262 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": 858110, "vin": [ { "gen": { "height": 858100 } } ], "vout": [ { "amount": 880559142, "target": { "key": "233c7f514438059262250ab42a032451a43c1f2a9c36717102edb1c67ad7a509" } } ], "extra": [ 1, 12, 117, 158, 136, 230, 212, 134, 185, 212, 161, 214, 194, 237, 59, 211, 86, 114, 28, 127, 61, 9, 154, 164, 86, 186, 163, 177, 169, 17, 8, 121, 32, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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