Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4da9783ba7ff6a7930a5d1502b5ca19cb25b3bab63173e3c9fb3e7d6d92897d2

Tx prefix hash: 9d559403c5d0efe88c121ea8e8bb973c4918022776be3ccdc6610482f19cfdac
Tx public key: 014e7d6f1a3cfde764930afb15fcbefe381ada1ecf8d1fb8b2b00a9e015cb0a4
Timestamp: 1702948898 Timestamp [UCT]: 2023-12-19 01:21:38 Age [y:d:h:m:s]: 01:338:17:01:13
Block: 916189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500938 RingCT/type: yes/0
Extra: 01014e7d6f1a3cfde764930afb15fcbefe381ada1ecf8d1fb8b2b00a9e015cb0a4021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1845f407e00f536e9000603052c324bd781b657dfc05c235fc051a9af4cd88d6 0.600000000000 1373671 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": 916199, "vin": [ { "gen": { "height": 916189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1845f407e00f536e9000603052c324bd781b657dfc05c235fc051a9af4cd88d6" } } ], "extra": [ 1, 1, 78, 125, 111, 26, 60, 253, 231, 100, 147, 10, 251, 21, 252, 190, 254, 56, 26, 218, 30, 207, 141, 31, 184, 178, 176, 10, 158, 1, 92, 176, 164, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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