Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00a86680ed6dd9bafc9b2946bdce3142a76381d9d70a001225a3fe85fa1fa726

Tx prefix hash: 67280e5c63450393177c5a5b2f7893d38141341575fdc922b64a41b278a66dc6
Tx public key: ea48d800c40ecac993244b88e9d6c2d78e8c8c7dc1832f8dd39ea135afe4f2b4
Timestamp: 1717333568 Timestamp [UCT]: 2024-06-02 13:06:08 Age [y:d:h:m:s]: 00:309:01:25:58
Block: 1035465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220863 RingCT/type: yes/0
Extra: 01ea48d800c40ecac993244b88e9d6c2d78e8c8c7dc1832f8dd39ea135afe4f2b402110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7af97437e72663b02809116b60503645a428a6649c9caf54ee1bc765f8dcc458 0.600000000000 1503986 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": 1035475, "vin": [ { "gen": { "height": 1035465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7af97437e72663b02809116b60503645a428a6649c9caf54ee1bc765f8dcc458" } } ], "extra": [ 1, 234, 72, 216, 0, 196, 14, 202, 201, 147, 36, 75, 136, 233, 214, 194, 215, 142, 140, 140, 125, 193, 131, 47, 141, 211, 158, 161, 53, 175, 228, 242, 180, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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