Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27d37d3f1d048ed20b1c6a534e42a681b4cbd9e5dfcd5dc9048bc088e663ab0c

Tx prefix hash: 5ed887f7e48e366234cc8000528eb37342003f0e2e7a0908384362872ddee77c
Tx public key: 715ddacfc1a635889c7c7a121cc1af6cef92deb22a4fa3fe181d25a6e97838f9
Timestamp: 1702915754 Timestamp [UCT]: 2023-12-18 16:09:14 Age [y:d:h:m:s]: 02:016:15:43:44
Block: 915922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 531693 RingCT/type: yes/0
Extra: 01715ddacfc1a635889c7c7a121cc1af6cef92deb22a4fa3fe181d25a6e97838f902110000000533af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: faecd950e640fb34c85d8951fdd317ebf700e88d8d9e9e8211339b4cb35b974a 0.600000000000 1373356 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": 915932, "vin": [ { "gen": { "height": 915922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "faecd950e640fb34c85d8951fdd317ebf700e88d8d9e9e8211339b4cb35b974a" } } ], "extra": [ 1, 113, 93, 218, 207, 193, 166, 53, 136, 156, 124, 122, 18, 28, 193, 175, 108, 239, 146, 222, 178, 42, 79, 163, 254, 24, 29, 37, 166, 233, 120, 56, 249, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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