Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ae9460421983272e0377153f4fd8ed4cceabdbabf710b097393d7d0536893e0

Tx prefix hash: 92f6ececf26d999d1a88270fcf059af26ab05e0d2c61fc6ff87c5513b6a2c5e7
Tx public key: c58b28fa4273e5a3e0d9f16142793ea66921d8c3f383dc227ac1aaa92db11835
Timestamp: 1639256619 Timestamp [UCT]: 2021-12-11 21:03:39 Age [y:d:h:m:s]: 03:030:08:03:15
Block: 393438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 800652 RingCT/type: yes/0
Extra: 01c58b28fa4273e5a3e0d9f16142793ea66921d8c3f383dc227ac1aaa92db11835021100000001408d5ef5000000000000000000

1 output(s) for total of 30.505415392000 dcy

stealth address amount amount idx
00: 1fcf37140bde40409511381a1934d6b1ba72306120c1a565253a74f6ce15ba36 30.505415392000 790669 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": 393448, "vin": [ { "gen": { "height": 393438 } } ], "vout": [ { "amount": 30505415392, "target": { "key": "1fcf37140bde40409511381a1934d6b1ba72306120c1a565253a74f6ce15ba36" } } ], "extra": [ 1, 197, 139, 40, 250, 66, 115, 229, 163, 224, 217, 241, 97, 66, 121, 62, 166, 105, 33, 216, 195, 243, 131, 220, 34, 122, 193, 170, 169, 45, 177, 24, 53, 2, 17, 0, 0, 0, 1, 64, 141, 94, 245, 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