Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee7bc61c0bf5d7466095f0bad8d8e0abdf2e5ba5341c6a8ef3c0422ca3befcc7

Tx prefix hash: 8ef746d7c2d1d400cf4dd6ac17f617fae0421431faaca006913ecfec796f58e6
Tx public key: f773a640972a22f4d9188c4dade8dcae929706225b0beda6dd51a6d527a0a000
Timestamp: 1672659546 Timestamp [UCT]: 2023-01-02 11:39:06 Age [y:d:h:m:s]: 01:336:07:57:22
Block: 665945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501396 RingCT/type: yes/0
Extra: 01f773a640972a22f4d9188c4dade8dcae929706225b0beda6dd51a6d527a0a000021100000005faf35c9c000000000000000000

1 output(s) for total of 3.814588817000 dcy

stealth address amount amount idx
00: 96518f548803479a98aa28c067da4779578e29ea835ad37ecdb813aa7de78643 3.814588817000 1107016 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": 665955, "vin": [ { "gen": { "height": 665945 } } ], "vout": [ { "amount": 3814588817, "target": { "key": "96518f548803479a98aa28c067da4779578e29ea835ad37ecdb813aa7de78643" } } ], "extra": [ 1, 247, 115, 166, 64, 151, 42, 34, 244, 217, 24, 140, 77, 173, 232, 220, 174, 146, 151, 6, 34, 91, 11, 237, 166, 221, 81, 166, 213, 39, 160, 160, 0, 2, 17, 0, 0, 0, 5, 250, 243, 92, 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